1 link tagged with all of: claude + context switching + engineering leadership + greptile + code review
Links
A veteran engineering leader lists practices he used to reject, like skipping human PR review, splitting teams across separate work streams, and going shallow instead of deep, that now work well because AI tools like Claude have cut the cost of context switching and code review. He admits his gut instincts may be less reliable than they were.
- Code review was replaced for about a month by having Claude author PRs and the ticket owner review them, with Greptile and CI as additional checks. The ticket owner understands the problem best, and the tools catch small bugs well, though big architectural issues are still rare.
- Splitting the team into parallel work streams no longer creates knowledge silos, because a new person can ask Claude to summarize a colleague's work and get up to speed in minutes. The real skill is now grasping the problem and solution shape rather than the code.
- Deep specialization in one framework matters less, since AI can answer framework questions instantly. Strong engineering fundamentals like abstraction design and judgment, plus product, design, and user research skills, are now the baseline for value.
claude
code review
engineering leadership
greptile
context switching